main: Don't gdk_flush() after every main loop wait
authorBenjamin Otte <otte@redhat.com>
Fri, 17 Nov 2017 06:47:03 +0000 (07:47 +0100)
committerBenjamin Otte <otte@redhat.com>
Fri, 17 Nov 2017 07:07:10 +0000 (08:07 +0100)
For a start, this makes gtk_main() work different from g_main_loop_run()
calls.

But most importantly, modern GDK does proper syncing itself and doesn't
need to rely on a catch-all to get it right.

gtk/gtkmain.c

index 5837f7ceb53ad3d87fd5d2c347f623113f1dbacf..a80201c774c3af87bb86c573af84c3a82f073e58 100644 (file)
@@ -986,7 +986,6 @@ gtk_main (void)
       gdk_threads_leave ();
       g_main_loop_run (loop);
       gdk_threads_enter ();
-      gdk_flush ();
     }
 
   main_loops = g_slist_remove (main_loops, loop);